<META HTTP-EQUIV="PICS-Label" CONTENT='(PICS-1.1 "http://www.rsac.org/ratingsv01.html" l comment "RSACi North America Server" by "inet@microsoft.com" r (n 0 s 0 v 0 l 0))' />
<META NAME="DESCRIPTION" CONTENT="Microsoft Windows 2000 Terminal Services provides access to Windows-based applications for a variety of client hardware devices. Applications are installed on the server and accessed by clients through terminal emulation. Each device that initiates a Terminal Services session must be licensed with a Windows 2000 Server Client Access License (CAL) and either a Windows 2000 license or a Terminal Services CAL. Clients may also gain access through a Windows 2000 Terminal Services Internet Connector license.">
<TD WIDTH="10"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD WIDTH="10"><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/1ptrans.gif" WIDTH="10" HEIGHT="1" /><!--mstheme--></font></TD>
<TD><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/1ptrans.gif" WIDTH="10" HEIGHT="1" /><!--mstheme--></font></TD>
<TD WIDTH="100%"><!--mstheme--><font face="Times New Roman"><A CLASS="NavLink" HREF="file:///D:/Documents and Settings/ericbrus/My Documents/My Webs/myweb12/server/features/exploring.asp" target="_top">Technologies in Depth</A><!--mstheme--></font></TD>
<TD WIDTH="15"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD WIDTH="10"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD WIDTH="10"><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/1ptrans.gif" WIDTH="10" HEIGHT="1" /><!--mstheme--></font></TD>
<TD><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/1ptrans.gif" WIDTH="10" HEIGHT="1" /><!--mstheme--></font></TD>
<TD WIDTH="100%"><!--mstheme--><font face="Times New Roman"><A CLASS="NavLink" HREF="file:///D:/Documents and Settings/ericbrus/My Documents/My Webs/myweb12/server/features/choosing.asp" target="_top">Choosing the Right Server</A><!--mstheme--></font></TD>
<TD WIDTH="15"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD WIDTH="10"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD CLASS="NavItemSelected" COLSPAN="3"><!--mstheme--><font face="Times New Roman"><A CLASS="NavLink" HREF="/windows2000/upgrade/default.asp" TARGET="_top">Upgrading to Windows 2000</A><!--mstheme--></font></TD>
<TD WIDTH="15"><!--mstheme--><font face="Times New Roman"> <!--mstheme--></font></TD>
<TD WIDTH="20" VALIGN="TOP"><!--mstheme--><font face="Times New Roman">
<A HREF="mailto:?subject=An article from Microsoft&body=This article is from the Microsoft Windows 2000 Web site. http://www.microsoft.com/windows2000/guide/server/pricing/tsfaq.asp"><IMG SRC="/windows2000/images/icoEmail2.gif" WIDTH="20" HEIGHT="15" BORDER="0"></A>
<!--mstheme--></font></TD>
<TD VALIGN="TOP" NOWRAP><!--mstheme--><font face="Times New Roman">
<A CLASS="finePrint" HREF="mailto:?subject=An article from Microsoft&body=This article is from the Microsoft Windows 2000 Web site. http://www.microsoft.com/windows2000/guide/server/pricing/tsfaq.asp">Send this document<BR />to a colleague</A><BR />
<!--mstheme--></font></TD>
<TD WIDTH="15"><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/ts.gif" WIDTH="15" HEIGHT="1" /><!--mstheme--></font></TD>
<TD WIDTH="28" VALIGN="TOP" NOWRAP><!--mstheme--><font face="Times New Roman">
<A HREF="file:///D:/Documents and Settings/ericbrus/My Documents/My Webs/myweb12/server/pricing/tsfaq.asp"><IMG SRC="/windows2000/images/icoPrinter.gif" WIDTH="22" HEIGHT="15" BORDER="0"></A>
<!--mstheme--></font></TD>
<TD VALIGN="TOP" NOWRAP><!--mstheme--><font face="Times New Roman">
<A CLASS="finePrint" HREF="file:///D:/Documents and Settings/ericbrus/My Documents/My Webs/myweb12/server/pricing/tsfaq.asp">Printer-friendly<BR>version</A><BR>
<!--mstheme--></font></TD>
<TD WIDTH="15"><!--mstheme--><font face="Times New Roman"><IMG SRC="/windows2000/images/ts.gif" WIDTH="15" HEIGHT="1" /><!--mstheme--></font></TD>
<!--mstheme--></font></TD>
</TR>
</TABLE><!--mstheme--><font face="Times New Roman">
<TR><TD><!--mstheme--><font face="Times New Roman"><!--msthemeseparator--><p align="center"><img src="../../_themes/copy-of-tilt/atlrule.gif" width="600" height="10"></p><!--mstheme--></font></TD></TR>
</TABLE><!--mstheme--><font face="Times New Roman">
<SPAN CLASS="field" ID="fld_bodycopy">
<P>Microsoft® Windows® 2000 Terminal Services provides access to Windows-based applications for a variety of client hardware devices. Applications are installed on the server and accessed by clients through terminal emulation. Each device that initiates a Terminal Services session must be licensed with a Windows 2000 Server Client Access License (CAL) and either a Windows 2000 license or a Terminal Services CAL. Clients may also gain access through a Windows 2000 Terminal Services Internet Connector license.</P>
<P><B>Q: What is Terminal Services License Management?</B></P>
<P>Terminal Services uses the Terminal Services Licensing service to obtain and manage its licenses for devices that connect to a terminal server configured in application server mode. (When using Terminal Services in remote administration mode, two concurrent connections are automatically allowed to log on, and a license server is not required.)</P>
<P>Terminal Services Licensing contains two primary components: the Terminal Services Licensing service and the Terminal Services Licensing administration utility (referred to here collectively as TSL). TSL manages unlicensed, pre-licensed, and temporarily licensed clients, as well as clients using a CAL. TSL supports both ordinary CALs and Internet Connector Licensing for Terminal Services. The licensing service simplifies the task of license management for the system administrator. It also helps administrators determine how many licenses to purchase.</P>
<P><B>Q: I am deploying Terminal Services using one of the Windows 2000 server products (not a 120-day evaluation version). What do I do about Terminal Services Licensing?</B></P>
<P>You must use TSL when connecting to Terminal Services in application server mode using any of the final (non-evaluation) Windows 2000 server products. TSL provides you with tools to manage Terminal Services CAL deployment and ensures that all clients accessing Windows 2000 Terminal Services are properly licensed with the necessary Terminal Services CALs.</P>
<P><B>Q: I am deploying Terminal Services using one of the Windows 2000 server 120-day evaluation products. Is there anything special I must do for Terminal Services Licensing?</B></P>
<P>The Windows 2000 Server family evaluation product End User License Agreement (EULA) provides the customer with 10 Terminal Services CALs and 10 Server CALs. The 10 Terminal Services CALs are valid for 90 days from the date the client first connects to the evaluation Windows 2000 terminal server. A maximum of 10 concurrent connections using any connection method can be made to the server, including File and Print, Web, and Terminal Services connections.</P>
<P>Customers who are evaluating Windows 2000 Terminal Services in Application Server mode using the evaluation product do not need to install or activate TSL on a Windows 2000 server. They can use the 10 Terminal Services CALs provided by the EULA because a 90-day grace period for Terminal Services is built into the Windows 2000 server.</P>
<P><B><I>It is not necessary to install Terminal Services CALs</I></B>. Do not install any purchased Terminal Services CALs onto an evaluation product Windows 2000 server.</P>
<P><B>Caution</B>. The installation of purchased Terminal Services CALs onto a TSL server that resides on an evaluation version of Windows 2000 will result in the loss of those licenses when the evaluation period expires. (Note that the terminal server will log System Error 1004 during the evaluation period. You can ignore this system error when using an evaluation product.)</P>
<P><B>Q: Where can I find technical details about TSL?</B></P>
<P>You can find detailed information about TSL, including information about how to request a license re-issue, in the <a href="/windows2000/library/howitworks/terminal/tslicensing.asp">Microsoft Windows 2000 Terminal Services Licensing</a> white paper.</P>
<P><B>Q: Where can I find deployment help for TSL?</B></P>
<P>You can find technical help about deploying TSL in the <a href="/windows2000/library/resources/reskit/dpg/default.asp">Deployment Planning Guide</a>. You can find additional deployment information in the "Windows 2000 Deployment Planning Guide" chapter of the Windows 2000 Resource Kit (located on the Windows 2000 Server, Advanced Server, and Datacenter CDs as part of Support Tools; also scheduled to be published by Microsoft Press in the first half of 2000).</P>
<P><B>Q: Which Windows 2000 products feature Terminal Services?</B></P>
<P>Only the Windows 2000 Server family features integrated Terminal Services. These products include Windows 2000 Server Standard Edition, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server.</P>
<P><B>Q: What if I want to have Terminal Services on my Windows 2000 Professional machine?</B></P>
<P>A workstation running Windows 2000 Professional is pre-licensed as Windows 2000 Terminal Services client. A Windows 2000 Professional machine cannot be configured as a terminal server.</P>
<P>You must buy a Windows 2000 Server or BackOffice CAL for each device that connects to a Windows 2000 terminal server. When you purchase a Windows 2000 Terminal Services CAL for a device, you are purchasing the right to access Windows 2000 Terminal Services on that device. If you already own a Windows 2000 operating system license for a specific device, you are licensed to run the operating system either locally or through a Windows 2000 terminal server.</P>
<P><B>Q: What licenses are required to run Terminal Services in Windows 2000?</B></P>
<P>Four product licenses are associated with Terminal Services in Windows 2000. You are required either to have #1, #2, and #3 or to have #1 and #4.</P>
<OL>
<LI><B>Windows 2000 Server</B> is required for hosting Terminal Services sessions.</LI>
<LI>A <B>Windows 2000 CAL</B> or a <B>BackOffice® CAL</B> is required to access both Windows 2000 Terminal Services and other basic network/application services in the Windows 2000 operating system.</LI>
<LI>A <B>Windows 2000 Terminal Services CAL</B> or a <B>Windows 2000 Professional license</B> is required to access Windows 2000 Terminal Services.</LI>
<LI>A <B>Windows 2000 Terminal Services Internet Connector license</B> is available to certain customers for non-commercial, non-employee, Internet use only. Per-user authentication is not allowed with this license. Clients connecting using the Terminal Services Internet Connector license are not required to have license #2 or #3 above.</LI>
</OL>
<P>For more information about Microsoft's product licensing, see <a href="file:///D:/Documents and Settings/ericbrus/My Documents/My Webs/myweb12/server/pricing/default.asp">Windows 2000 Server Pricing & Licensing</a>.</P>
<P><B>Q: Why is Microsoft developing TSL?</B></P>
<P>TSL is Microsoft's first step in developing integrated licensing technologies within the Windows operating system. This new technology helps you in accounting for and properly licensing Terminal Services clients and helps Microsoft ensure that only licensed clients can access Terminal Services.</P>
<P><B>Q: What are the components of TSL, and what do they do?</B></P>
<P>The four primary components of the TSL service are the following:</P>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Client</B>. The Terminal Services client is a PC, a Windows-based terminal, or another device that runs the client software. The client is the machine to which the Terminal Services CAL is issued.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Terminal server</B>. The terminal server is a Windows 2000 server machine that has Terminal Services enabled in application server mode. The Terminal server provides multiple clients with access to Windows-based applications running on the server. The terminal server validates a client machineÆs license. If the client does not have a license, the terminal server requests one for the client from the license server.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>License server</B>. The Terminal Services license server is a Windows 2000 server machine that has the TSL component installed. This machine tracks and deploys client licenses. One license server can serve multiple terminal servers concurrently.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Microsoft Clearinghouse</B>. The Microsoft Clearinghouse is the database that Microsoft maintains to issue digital certificates (which let you install licenses securely) and license key packs to Terminal Services license servers that request them.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--></table><!--mstheme--><font face="Times New Roman">
<P><B>Q: What is a "license key pack"?</B></P>
<P>A license key pack is a digital representation of one or more licenses. Once a license key pack is installed on your license server, the license server can issue those licenses to clients.</P>
<P><B>Q: How do I get TSL up and running?</B></P>
<P>Complete these five steps to set up TSL:</P>
<OL>
<LI><B>License Purchase</B>. Purchase Terminal Services licenses. You can buy them either as part of the packaged product through a reseller or through one of Microsoft's many volume licensing programs. You can also obtain licenses through Microsoft Developer's Network (MSDN) subscriptions and other special Microsoft programs.</LI>
<LI><B>License server setup</B>. Install the Terminal Services Licensing component on a Windows 2000 server. You can do this either during initial system setup or later using Add/Remove Programs.</LI>
<LI><B>License server activation</B>. Activate a license server by requesting a limited-use digital certificate from Microsoft Clearinghouse. This digital certificate lets the license server install licenses in a secure fashion. (See the next question for more about activating a license server.)</LI>
<LI><B>License installation</B>. Make a connection to Microsoft Clearinghouse and provide purchase information. Microsoft Clearinghouse validates this information and you can then install the licenses on the license server.</LI>
<LI><B>License distribution</B>. After Terminal Services CALs are installed on the license server, the license server issues the licenses to terminal services clients on an as-needed basis. A terminal server can also be enabled as an Internet Connector after the Terminal Services Internet Connector license has been installed on the license server.</LI>
</OL>
<P><B>Q: What does it mean to ôactivateö a license server?</B></P>
<P>Acquiring Terminal Services licenses from the Microsoft Clearinghouse is a secure, trusted transaction. To perform this transaction, a license server must establish an identity with the Clearinghouse. During "activation," a license server is issued a limited-use digital certificate. This certificate establishes the server's identity for future license transactions (this server identity is used only to ensure that a license is installed on the machine that requested it). Using this certificate, a license server can make subsequent transactions with Microsoft to receive client license key packs, which contain multiple Terminal Services CALs for distribution by the license server.</P>
<P><B>Q: How does the license server communicate with the Microsoft Clearinghouse?</B></P>
<P>You can use the following methods for the license server to communicate with Microsoft Clearinghouse:</P>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Internet</B>. Using an Internet connection is the fastest and easiest way to activate the license server and install licenses. This connection method, managed by the Licensing Wizard, uses a non-browser-based Internet connection from the machine running TSL. A persistent Internet connection from the license server is not required. You can easily establish a dial-up Internet connection, which requires only a few minutes, from a separate administration machine.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>World Wide Web</B>. Using the Web to activate the license server requires an Internet browser. You take information provided by the Licensing wizard and enter it into the URL supplied by the wizard. To complete the transaction, you can then print, copy, or save to a file license server the activation and/or license installation information from the Web site for use in the Licensing wizard.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Fax</B>. To use a fax to activate the license server, you enter required information into the Licensing Wizard, and then manually print and fax this information to a customer service number provided by the wizard. The customer service center then generates license server activation and/or license installation information and faxes it back to you. To complete the transaction, you enter it into the Licensing Wizard.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Telephone</B>. You can contact a customer service center at a number provided by the Licensing wizard and give them the required information. The customer service representative then gives you the license server activation and/or license installation information, which you enter into the Licensing wizard.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--></table><!--mstheme--><font face="Times New Roman">
<P><B>Q: How does TSL help improve the manageability of Terminal Services licenses?</B></P>
<P>TSL issues a digital license from a license key pack to a client when the client connects to a terminal server:</P>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Windows 2000 clients</B>. Client machines running Windows 2000 Professional are automatically issued Terminal Services "built-in" licenses. That is, Windows 2000 Professional machines are already licensed to run a terminal services session and do not need a Terminal Services CAL.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--></table><!--mstheme--><font face="Times New Roman">
<P>TSL tracks when the license was issued and to which machine it was issued. You can use this information to analyze license usage and to ensure license compliance.</P>
<P><B>Q: What licenses can I manage with TSL?</B></P>
<P>TSL manages only Terminal Services CALs and Terminal Services Internet Connector licenses for terminal servers in application server mode. TSL does not manage other licenses, such as file and print CALs or Microsoft Office licenses.</P>
<P><B>Q: How do I purchase licenses and install them on the Terminal Services license server?</B></P>
<P>The Licensing wizard supports the following methods for purchasing Terminal Services licenses (once the licenses are purchased, the TSL Licensing wizard guides you through the installation process):</P>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Select or Enterprise Agreement</B>. If you purchase software using a Microsoft Select or Enterprise Agreement, use your Enrollment Agreement number to request and install licenses. If you purchase software using a Microsoft Campus or School agreement, you should choose this option and use your agreement number to request and install licenses. The installation of licenses is not a purchase. You should report purchases of Terminal Services CALs as you would any other software purchase.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Open License</B>. If you purchase software using a Microsoft Open License, you must use the Authorization Number and License Number received from Microsoft under which you purchased your Terminal Services licenses.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--><tr><td valign="baseline" width="42"><img src="../../_themes/copy-of-tilt/atlbull1.gif" width="15" height="15" hspace="13" alt="bullet"></td><td valign="top" width="100%"><!--mstheme--><font face="Times New Roman"><B>Other</B>. This category includes licenses purchased at retail outlets or any other channel that provides a license code. License codes typically come as part of a Microsoft License Pak (MLP) purchased through retail channels. The Licensing wizard prompts the user for the license code in order to install licenses onto the TSL server. Customers who receive licenses through MSDN or other special Microsoft programs should consult their product or program packaging for TSL information specific to them.<!--mstheme--></font><!--msthemelist--></td></tr>
<!--msthemelist--></table><!--mstheme--><font face="Times New Roman">
<P><B>Q: What is a license code?</B></P>
<P>The license code is a 25-character alphanumeric code that represents a pre-purchased quantity of Terminal Services CALs. The license code is printed on a License Addendum Card accompanying the purchase of a Terminal Services CAL MLP. You must enter the license code into the Licensing wizard in the Terminal Services Licensing utility in order to install that quantity of Terminal Services CALs. You can use a license code only once. Save it with other software licensing documentation in case you need to contact customer service for licensing issues.</P>
<P><B>Q: I am using the Web connection method to install my Terminal Services CALs. The Web site is asking for a 35-character code, but I have only a 25-character code. Where do I find the 35-character code?</B></P>
<P>The 35-character code the Web site prompts you for is your license server ID (LSID). The Licensing wizard provides the LSID on the same screen that gives you the Web connection method URL. Your license server is assigned this ID (which is an alphanumeric equivalent of your limited-use digital certificate) during the license server activation process. After you provide the LSID, the Web site then prompts you for the 25-character license code.</P>
<P><B>Q: What if no Terminal Services CALs are available on the license server?</B></P>
<P>If your license server's pool of available licenses is depleted, the license server issues 90-day temporary licenses to unlicensed clients. The temporary license helps prevent a denial-of-service to a user and gives you time to account for and then purchase any additional required licenses. The license server tracks when and to which machine a temporary license is issued, as well as the date it will expire. You can review this information using the Terminal Services Licensing utility.</P>
<P><B>Q: What if I want to get Terminal Services for Windows 2000 set up right away, but I do not have time to set up a license server at the same time?</B></P>
<P>The Windows 2000 terminal server has a 90-day grace period before it must find a license server. During this grace period, the terminal server allows connections from unlicensed clients. If this 90-day grace period has passed and the terminal server still has not located a license server, the terminal server serves sessions only to clients that have been issued a license.</P>
<P><B>Q: Where is the CAL for the client machine stored?</B></P>
<P>The CAL is stored locally on the client machine. This is true whether the client machine is a PC, a Windows-based terminal, or a Citrix ICA client running on any device. (ICA, which stands for Independent Computing Architecture, is the presentation services protocol from Citrix Systems, Inc., that governs input/output between a client and server.)</P>
<P><B>Q: What happens if I have to re-install the client's operating system?</B></P>
<P>If you re-install the client's operating system, the license is preserved—unless you reformat the client machine or reset local flash memory on a Windows-based terminal. In both of these latter cases, the locally stored license is lost. To regain the lost license, request a license re-issue from a Microsoft TSL support representative. For information about the re-issuance process, see the white paper <a href="/windows2000/library/howitworks/terminal/tslicensing.asp">Microsoft Windows 2000 Terminal Services Licensing</a>.</P>
<P><B>Q: Is Microsoft going to deploy this technology with other products?</B></P>
<P>Microsoft may deploy secure licensing technologies to other products in the future based on product needs.</P>
<P><B>Q: How do I get licenses for testing and development if I am an MSDN subscriber?</B></P>
<P>If you are a subscriber to MSDN, or a recipient of an MSDN product, your kit contains information on how to obtain licenses for testing and development purposes.</P>
<P><B>Q: What does Microsoft do with the personal information I provide during license server activation and license installation?</B></P>
<P>Microsoft asks only for company (not personal) information regarding the purchase and installation of licenses. The company information you provide during the licensing process is used only by a telephone customer support representative to help you if you need assistance. For more information on Microsoft's privacy policy for TSL, search for "Terminal Services Privacy" in Windows 2000 on-line help, or see our <!--<a href="https://activate.microsoft.com/">-->TSL Web site<!--</a>--> and click on the privacy shortcut.</P>
<P><B>Q: If I have a Microsoft Enterprise, Campus, or School Agreement and want to deploy Windows 2000 Terminal Services, do I need to buy Terminal Services CALs for the client machines covered under my agreement?</B></P>
<P>Microsoft Enterprise Agreement versions 4.0 and 4.1 and Campus and School Agreement customers are licensed for Windows 2000 Professional for each of the client devices included in their agreement. Windows 2000 Professional is a valid license for accessing a Windows 2000 terminal server—so, no, you do not need to purchase Terminal Services CALs for those client devices.</P>
<P>TSL technology does require deployment of Terminal Services CALs to any client device that is not running Windows 2000 Professional. Although client devices covered by Microsoft Enterprise Agreements are properly licensed for Windows 2000 Professional, Terminal Services CALs must still be installed on a license server for deployment to these clients. It is important to understand that a requirement to deploy Terminal Services CALs through the TSL technology in this case—that is, when a client device is covered under an Enterprise, Campus, or School agreement and is therefore licensed for Windows 2000 Professional but is not physically running Windows 2000 Professional—does not require an additional purchase of Terminal Services CALs.</P>
<P>You should install the appropriate number of Terminal Services CALs onto the license server to deploy Windows 2000 Terminal Services to those client devices that are licensed for Windows 2000 Professional but are not physically running the operating system. When installing licenses, you should designate "Microsoft Select or Enterprise Agreement" as the licensing program through which Terminal Services CALs were purchased, and supply the appropriate Enrollment Agreement, Campus, or School agreement number in the field labeled "Enrollment Number."</P>
<P><B>Q: If I have a Microsoft Campus Agreement and want to provide faculty and staff access to Windows 2000 terminal servers from home in accordance with our Campus Agreement's home-use clause, do I need to buy Terminal Services CALs for those home computers?</B></P>
<P>Microsoft Campus and School Agreement customers are licensed for faculty and staff home use through their agreement. You do not need to purchase Terminal Services CALs for those home devices because they are licensed for Windows 2000 (even though the devices are not actually running the operating system). However, you may need to install and deploy Terminal Services CALs under the same requirements as the school- or campus-owned client devices.</P>
<P><B>Q: I need to transfer a Terminal Services CAL internally in my company from one client device to another. How do I accomplish this?</B></P>
<P>The Terminal Services CAL End User License Agreement (EULA) is a per-seat license. It does allow for a one-time permanent transfer of the license to another client device. To receive a re-issue of this license, you contact a Microsoft Customer Services Representative (CSR) in the TSL Customer Service Center (CSC) and request a re-issue for the number of necessary Terminal Services CALs. For Windows 2000 Terminal Services, you can complete this re-issue process only over the telephone. You can complete this process on a periodic basis, retrieving multiple licenses in one call and making use of the 90-day temporary client license, if necessary. A re-issued set of Terminal Services CALs is displayed in the TSL administration tool as another license key pack installation. Aside from being a separate license key pack installation, re-issued Terminal Services CALs are indistinguishable from an original installation.</P>
<P>To find the phone number for the CSC nearest you so you can receive and install your re-issued licenses, open the TSL administration tool on your Windows 2000 server. From the <B>View</B> menu, click <B>Properties</B>, and then choose the <B>Connection Method</B> tab. From the drop-down box, choose <B>Telephone</B> and select your country. Click <B>OK</B>. From the <B>Action</B> menu, click <B>Install Licenses</B> to start the Licensing wizard and obtain the telephone number. Call the CSC and the CSR will guide you through the process of receiving a re-issued license.</P>
<P><B>Q: I have purchased Version 4 Terminal Services CALs and Upgrade Advantage on those Version 4 Terminal Services CALs through Microsoft Open License. How do I install the Windows 2000 Terminal Services CALs that I am authorized for through Upgrade Advantage?</B></P>
<P>Microsoft Open License Program customers who have purchased Upgrade Advantage on their Terminal Services Version 4 CALs should use the License number and Authorization number with which they purchased the Upgrade Advantage. These License and Authorization numbers will let you install the Windows 2000 Terminal Services CALs associated with the version 4 Terminal Services CAL Upgrade Advantage.</P>
</SPAN>
<!--end of main content area-->
<!--mstheme--></font></TD>
<TD WIDTH=15><!--mstheme--><font face="Times New Roman"><IMG WIDTH="15" HEIGHT="1" ALT="" SRC="/windows2000/images/1ptrans.gif" /><!--mstheme--></font></TD>
</TR>
<TR>
<TD WIDTH="100%" VALIGN="TOP"><!--mstheme--><font face="Times New Roman">
